home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
BBS Toolkit
/
BBS Toolkit.iso
/
remote
/
pnbrd102.zip
/
DR2RA100.ZIP
/
DOORTORA.DOC
next >
Wrap
Text File
|
1991-12-14
|
5KB
|
107 lines
DoorToRA, A DorInfo1.DEF to Remote Access files convert, to allow
you to run Remote Access doors on systems that support
the DorInfo1.Def kind of exitfile.
(c) 1991 Hans Siemons, Prime Productions
@Fido 2:285/214
@SIGnet 27:3331/3100
@RiftNet 62:1001/0
@Parabel 9:77/1000
BBS Tel +31-76-715391 [HST/V32bis] (Prime BBS)
Snailmail:
J.A.J. Siemons,
Crogtdijk 1,
4815 AD, Breda.
The Netherlands.
BankAccount 222140607
GiroAccount 5145504
Because of the toolkit I use my doorgames would only work on
Remote Access systems, and there was more and more pressure every
day to make my (other say fun) doors compatible with other bbs-
systems. Well, instead of doing that I created a front/end program
to take care of things. It creates the necassary Remote Access
1.10 system files out of a DorInfo1.DEF file.
DoorToRA reads the following DorInfo1.DEF.
System name
First name Sysop
Last name Sysop
Compoort (com0 for local)
Baudrate Linesettings
0 (I thought WantsChat, not used anyway)
First name user
First name sysop
Location User
Graphics (0=no,1=ansi,2=avatar,3=ansi+avatar)
Seclevel
Time left.
and creates the following files in the directory where DoorToRA is
located:
Config.RA (Setupfile for Remote Access)
Languages.RA (File with language definitions)
English.RAL (File with English language text)
ExitInfo.BBS (RA 1.10 compatibly Exitinfo file)
UserOn.BBS (File with info about current user)
After creating those files, it will make the directory where
DoorToRA is located the current directory, and executes the sub-
door. After the subdoor exits, DoorToRA removes the files it has
created and restores the original directory.
Keep in mind that some programs maintain the Remote Access logfi-
le. They now do it in a logfile named 'ra.log' which is created in
the directory where DoorToRA is created.
How to install...
Not that difficult... Start up DoorToRA like this:
DOORTORA.EXE <Subdoor> <Parameters for subdoor>
Sample for Shuffle:
<Path>\DoorToRA.EXE c:\bbs\doors\shuffle\shuffle.exe
DoorToRa will pass on all parameters on the commandline, since it
hasn't any of it's own.
Legal stuff: As usual... No guarentees what soever... You're on
your own.
DoorToRA is spreaded under a 'thanks a lot' basis. You like it?
Let me know, some place, somewhere... That's all I'm asking. Feel
free to use it in any environment, commercial, noncommercial or
something inbetween. DoorToRA was easy, but extremely boring to
write. If you feel that DoorToRA is worth money to you, you're
free to donate anything to me or to your favorite charity.
I do accept flames, but *NOT* in echomail. If you have anything
bad to say about either DoorToRA or just about me, feel free to do
it per private netmail, or logon to my board and yell the shit out
of me! I wouldn't care less.
Thanks for reading, and good luck using this ! You'll definatly
need it <grin>
* Note for third party developers *
You are free to distribute DoorToRA together with your doors
and/or mention it in your documentation, and you are allowed to
alter the documentation at one point: The example. I do expect to
receive a free registration of your door from you for those doors
spread together with DoorToRA since you will probarly reach a
bigger public with your doors, and as a result of that you probar-
ly will receive more registrations. A free registrationkey of your
door is not a lot to ask then! (I have set the following informa-
tion in RAConfig: Sysop: Hans Siemons, Systemname: Prime BBS).
Thanks in advance!
//The End//